enhancement(ruleset): add support for category-level ruleset expansion with docker/all syntax #471
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why This Change?
Users currently must manually specify each bundle individually when they want to run all rules for a technology:
This is tedious and error-prone. Users want a simple way to run ALL rules for a category with a single flag.
Summary of Changes
New Feature: Support
category/allsyntax (e.g.,docker/all,python/all) to automatically expand to all bundles in that category.Implementation:
ManifestProviderinterface for testability and dependency injectionParseSpec()to detect "all" keyword → converts to internal marker "*"GetAllBundleNames()helper to Manifest for retrieving all bundle namesexpandBundleSpecs()function with interface-based design for easy testingUsage Examples:
Testing:
Files Changed: 7 files, +353 lines